Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix disaggregation #674

Merged
merged 19 commits into from
Oct 26, 2023
Merged

Fix disaggregation #674

merged 19 commits into from
Oct 26, 2023

Conversation

ClaraBuettner
Copy link
Contributor

The original PR to disaggregate links and stores (#629) included some problems, e.g. 95c22f0 assumed that etrago.clustering.busmap is a pandas.Series, but it is a dictionary.
In addition, some commits from https://github.com/openego/eTraGo/tree/features/disaggregate-links-and-stores-update-busmap were not part of the merged branch.
I fixed those problems in this branch.
This branch also solves #644

Copy link
Contributor

@CarlosEpia CarlosEpia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using the default arguments but with 50 snapshots, the disaggregation shows an error:
"Sum of disaggregated time series does not match..." Do you know what could be the reason?

etrago/cluster/disaggregation.py Show resolved Hide resolved
This es especially needed when all generators are PQ-controlled (e.g. load shedding) and there is no reactive power time series that needs to be distributed
This happens within the pf_post_lopf anyhow. But before, the change was only done for the aggregated and not the disaggregated network which resulted into problems when disaggregating
Copy link
Contributor

@CarlosEpia CarlosEpia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested this branch and it ran OK. It was not tested when PF post LOPF is activated.

@ClaraBuettner
Copy link
Contributor Author

The problems when disaggregating load_shedding generators after the pf_post_lopf occur because the control strategies for generators are set multiple times, and sometimes different.
That resulted in different control strategies for load_shedding generators in the aggregated and the disaggregated network.
I think it is the best solution to set the control strategies only once, and at a central place. I will look for that, change the code and inform you when it is done.

The control parameters are overwitten within pypsa's network clustering, because slack generators are selected.
In order to not keep this change, the function set_contro_strategies needs to be called again after every
spatial clustering.
@ClaraBuettner
Copy link
Contributor Author

I tested this branch and it ran OK. It was not tested when PF post LOPF is activated.

I fixed the problems, it now also works when the pf was executed.

@ClaraBuettner ClaraBuettner merged commit 94acf8d into dev Oct 26, 2023
6 checks passed
@ClaraBuettner ClaraBuettner deleted the fixes/fix-disaggregation branch October 26, 2023 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants